Reconfiguring operations
It is possible to reconfigure operations that are already part of a data recipe. Perhaps the values of a field need to be changed, a field needs to be added or removed from the dataset, or field names and types have changed. This is achieved using the reconfigure option, which will open the configuration dialog where the changes can be made.
Note: How you reconfigure the operation has different effects on subsequent datasets.
Accessing the Reconfigure menu
Set [Change View] option: Full View, listing operations
-
Set the view of the datasets in the canvas to [Full view].
-
The operations that were performed on the dataset are listed.
-
A button with ellipses is active next to each operation that can be reconfigured.
-
Click the [...] button and the configuration dialog of that operation will show. The initial configuration settings are populated - make the configuration changes as necessary, using the configuration steps listed as a guide.
Context menu
-
Right click on the dataset on the canvas to access the Reconfigure option.
-
Click on [Reconfigure] to see the list of operations that were performed on the dataset.
-
Select the operation to reconfigure. The configuration dialog of that operation will show. The initial configuration settings are populated - make the configuration changes as necessary, using the configuration steps listed as a guide.
Effects of reconfiguration
In order for the data recipe to retain the same functionality, configuration changes can only be made to the:
-
values of fields, or
-
the number and order of rows within datasets.
These changes will have no effect on subsequent operations, or dependant child datasets.
Changes to the following aspects in a dataset will cause subsequent operations in the dataset to be lost, as well as dependant child datasets to be removed:
-
Field names being changed
-
Field types being changed
-
Fields being added to an operation
-
Fields being removed from an operation
If one of these aspects are changed, a warning dialog will show detailing the operations and datasets that will be dropped. If there are no datasets or operations that will be affected by the changes and dropped from the data recipe, no warning will show.
-
Click [OK] to continue with the reconfiguration, and drop all subsequent operations and datasets.
-
Click [Cancel] to return to the data preparation view, discarding your reconfiguration changes.
Re-executing reconfigured operations
When operations are reconfigured, they need to be re-executed to ensure the integrity of the data recipe. The time taken to re-execute the data recipe is determined by the number of operations that need to be re-executed in all of the affected datasets.
Operations are re-executed as follows:
-
All operations in child datasets that are affected by the reconfiguration change will be re-executed.
-
Operations in datasets that are not affected by the reconfiguration will NOT be re-executed.
-
All the operations within an affected dataset are re-executed.
Effect of reconfiguration on loaded Troubleshooter project data
Previously loaded data for Troubleshooter projects will not automatically be updated with your reconfigured data recipe. You will need to reload your dataset in order to see the reconfigured data in your Troubleshooter for Steps 2 and further.
Related topics: